BBS Toolkit/BBS Toolkit.iso/doors_1/gc2f.zip/GC2.DOC

Text File | 1989-11-23 | 20KB | 516 lines

                       Galactic Conquest II
                           Documentation



Features

 o    Quick Instillation Guide found in file "FINSTALL.DOC"
 o    Directly compatible with PCBoard and GAP
 o    Compatible with GT, Wildcat, Opus, QuickBBS, RBBS, Auntie, etc.
      via 3rd party conversion programs
 o    Does not require CTTY or Watchdog
 o    Informative status line
 o    Automatic detection of multi-node systems
 o    Time calculations not susceptible to midnight roll over
 o    2,697 sector galaxy within game
 o    Up to 75 active players
 o    3 different rivaling nations (899 sectors each)
 o    4 different ranks for users to obtain
 o    Full-featured character/sector/setup editor
 o    3 different currency types and varying exchange rates between them
 o    Full-color chat mode with word wrap
 o    Galactic lottery
 o    E-Mail between users
 o    Users can booby trap sectors
 o    Orbiting reconnaissance satellites
 o    Anti-satellite missiles
 o    Multi-BBS interaction (exchange of intelligence information, credits,
      and E-mail)
 o    Users can place bounties on other users
 o    Use of aliases determined by Sysop
 o    Ranking bulletin can be created daily, weekly, or after each user plays
 o    Compiled under latest Qbasic compilers
 o    Users receive passport when traveling into a foreign nation
 o    Easily configured by the Sysop
 o    User's ship requires fuel to move, in addition to turns
 o    Sysop can define number of turns and winning requirements
 o    Online documentation for the user
 o    User may page Sysop if page bell is turned on in PCBoard or GAP
 o    Sysop defines winning requirements
 o    Support for up to 38,400 BPS!
 o    Support for COM1 thru COM4

       And more!


Configuration

The following files will be generated when you run GC2INIT:

    USER.GC2                    WA.GC2
    PORTS.GC2                    SETUP.GC2
    FSA.GC2                    RECONSAT.GC2
    EUGSR.GC2

The following files will be created when the game is run if you have Multi-BBS
Interaction on:

    BBSUL1.GC2                BBSUL3.GC2
    BBSUL2.GC2                BBSOUT.GC2

Two files, GC2ASCII and GC2ANSI, are created when the Bulletin Generator
(GC2BLGEN.EXE) is run.

You will need to create a configuration file for each node that will access
the game.  If you are not running a multi-node setup, you will need only
create one configuration file.  The format is the following:

    Path to BBS system files
    BBS name
    BBS type

The first line is the complete drive path for the location of your PCBoard or
GAP system files.  For those running Wildcat, QuickBBS, Opus, GT, RBBS, etc.,
this is the full path to where your GAP or PCB files are created and kept
(i.e. PCBOARD.SYS, PCBOARD.DAT, USERS etc.)

The second line is the name of your BBS system.

The third line is a "1" if you are running PCBoard, or wish to run the
door in PCBoard mode thru a conversion program.  Enter a "0" or anything
else to default to GAP mode.

You will need to create a separate configuration file for each node.  The only
difference should be line 1, since each node will have a different
subdirectory.

Galactic Conquest II was written using the GAPQBDR libraries for QB 4.5 from
GAP Communications Company.  Hence, the default operation mode is GAP.  If you
are running under PCBoard or are converting to PCBoard, you will need to set
the DOS environment variable GAPQBDR equal to PCB by typing SET GAPQBDR=PCB
exactly as shown here (in upper case and without spaces before or after the
equal sign).

You will need to edit your DOOR.LST file as well as DOOR and DOORG to add GC2
to PCBoard.  Edit any appropriate system files for your BBS system to define
GC2.  The basic batch file needed to call up Galactic Conquest II should
contain the following:

cd \gc2
gc2login %1
gc2 %1
gc2blgen
copy gc2ascii c:\blt\blt1
copy gc2ansi  c:\blt\blt1g
cd \bbs
loadbbs

Where %1 is the name of a configuration file, GC2LOGIN logs the user into the
game, displays news files, etc., allows him to play the lottery, and then
exits.  This is where GC2 is loaded and the rest of the game is played.  When
the user (Q)uits the game or drops carrier, the batch file exits and reloads
the bulletin board.

Optionally, if you do not want a high scores file generated each time the game
is run, remove the GC2BLGEN and the two copy commands from the batch file.

Here are some specific examples of the required batch file to load GC2 on
PCBoard, Wildcat, GAP, and Opus:

    For PCBoard:

cd \gc2
gc2login %1
gc2 %1
gc2blgen
copy gc2ascii c:\pcb\gen\blt9
copy gc2ansi c:\pcb\gen\blt9g
cd \pcb
board

    For Wildcat:

rem * run any of the numerous conversion programs which will
rem * translate Wildcat's CALLINFO to either PCBoard files
rem * or GAP files.
cd \wildcat\doors\gc2
gc2login %1
gc2 %    1
gc2blgen
copy gc2ascii c:\wildcat\bulletin\bullet9.bbs
copy gc2ansi  c:\wildcat\bulletin\bullet9.scr
cd \wildcat
cat

    For GAP:

cd \gc2
gc2login %1
gc2 %1
cd \gap
gap

    For Opus:

echo off
cd\opus\pcbdor
drlink /Lc:\opus\lastuser.bbs /Cc:\opus\drlink.ctl /Gc:\opus\gc\ cd\opus\gc
gc2login gc2.cfg
gc2 gc2.cfg
gc2blgen
copy gc2ascii+rtrnmenu.bot gc.bbs
copy gc2ansi+rtrnmenu.bot gc.gbs
cd\opus

Note:  The Opus batch file is courtesy of Mike Bloom, Sysop of The Exchange;
[phone]; Netmail address: 1:124/3220.  DRLINK is a program to convert
OPUS's LASTUSER.BBS to the appropriate GAP or PCBOARD system files.  It is
available on the backbone Software Distribution System.

Multi-Node Systems

Galactic Conquest II employs file sharing with any of the GC2 EXE files,
except GC2INIT, if you add a "/N" on the command line.  If you were running a
version 14.2/E9 PCBoard, your batch file for node 1 might look something like
this:

 L:
 cd \doors\gc2
 gc2login gc2.cfg /N
 gc2 gc2.cfg /N
 gc2blgen /N
 copy gc2ansi c:\blt\blt2g
 copy gc2ascii c:\blt\blt2
 c:
 board3


Function Keys

The following function keys are active while a user is online in the door:

[F5]    Shell to DOS.  You do not need to return to the same subdirectory
before you type EXIT.  The door will automatically return to the same drive
and subdirectory.

[F8]    Twit the user and return to the BBS.  This is the fastest way to get
return the user to the BBS.

[F10]    Initiate chat with user.  Chat occurs in full color with word wrap
active.

[CtrlFl0]    Answer page bell and chat with the user.

[Home]    Main user stats.

[End]    Displays Sysop's keys available.

[PgDn]    Secondary user's time remaining.

[UpArrw]    Increase user's time remaining.

[DnArrw]    Decrease user's time remaining.


Error Trapping

Error trapping is preformed by GC2, and any error that can be trapped is
trapped.  We have done our best to make sure the door will never hang your
system.  In addition, the various support programs contain logic to trap for
all errors and to write the corresponding error code, location, and time/date
to a file called GC2.ERR.  This file can be useful in determining the cause of
an error and likely remedies.  The numerical error codes correspond to their
BASIC equivelants.  Refer to the appendicies of your BASICA or GWBASIC manual
for a list of error codes.


Daily Maitenance

You should add GC2DAILY.EXE to your event batch file (create an
event if you don't have any active) to run at least once per day.

GC2DAILY gives users their days turns, replenishes ports etc.


Compatibility Issues

1) Galactic Conquest II uses the GAPQBDR I/O libraries which were designed
   to use DOS function calls to output text to the screen.  This should
   prevent any screen bleeds while using multi-tasking software.

2) GC2 requires you to have at least a "FILES=20" or greater in your
   CONFIG.SYS.

3) GC2 may not run on systems using an EGA card if the EGA card uses NMIs
   (non-maskable interrupts).  The NMIs can steal away interuppts from the
   GAPQBDR I/O routines.

4) GC2 will only run on COM1 thru COM4.

5) GC2 provides for file sharing if a multi-node system is being used if a
   "/N" is passed on the command line above.

6) For proper PCBoard emulation by a non-PCBoard system the PCBOARD.SYS,
   PCBOARD.DAT, and USERS must be present.

7) GC2 cannot be allowed to be active under more than one partition at once if
   you are running a 286 and are using DoubleDOS.  There is a bug in DoubleDOS
   that occurs only on 286s when a QuickBASIC 4.x program is loaded in a
   second partition, while a QuickBASIC 4.x program is active in the first.
   This is a problem not only with doors but with any application written in
   QuickBASIC 4.x.  If you are running this 286/DoubleDOS configuration, use
   logic in  the batch file to prohibit the game from running if it is already
   active on another node. Also, consider switching to a multi-tasker with
   less bugs, such as Omniview or Desqview.


Upgrading from GC 1.x to GC II

Because the format of the game changed so much between versions 1 and II, no
conversion programs are supplied to update the game's databases between the
two versions.

Multi-BBS Interaction

The following discusses how to implement multi-BBS interaction between two
BBSs running Galactic Conquest II.

Multi-BBS interaction allows users on two different bulletin boards to
interact with each other in the following ways--exchange of credits, E-mail,
and intelligence information.  Galactic Conquest II does not provide internal
means for moving the required data files between the two bulletin board
systems.  The Sysop will need to design a script or file request it (FidoNet
boards) to exchange the files listed below.  Every night each system should
run GC2DAILY.  This will give the users new turns and also shut multi-BBS
interaction off until the data files are exchanged and incorporated.  System A
and System B should connect to each other and exchange the following files:

    BBSUL1.GC2    BBSUL2.GC2
    BBSUL3.GC2    RECON1.GC2
    RECON2.GC2    RECON3.GC2
    GC2LOCD       BBSOUT.GC2

Each of these files, once arced, should be deleted so as not to mix them up
when unarcing the packet from the other system, and so they are not appended
the next time GC2 is run.  Packets should then be exchanged.  Each system
should unarc the files into a temporary (non-GC2) subdirectory.  Using the DOS
copy command, your batch file needs to copy BBSUL.GC2 + BBSUL2.GC2 +
BBSUL3.GC2 into GC2ULST.  Copy RECON? + GC2LOCD into the file GC2UNTL.  Rename
BBSOUT.GC2 to BBSIN.GC2.  Next copy GC2UNTL, GC2ULST, and BBSIN.GC2 to your
GC2 subdirectory.  Delete all of the files in the temporary directory and
switch to the GC2 subdirectory.  Then run the program GC2IMPRT.  This imports
the other systems' users' commands into the various users' mail boxes and user
records.  It also updates the list of users on the other system (GC2ULST) and
the intelligence information (GC2UNTL).  The archive you downloaded from the
other system can now be deleted.  GC2IMPRT also unlocks multi-BBS
interaction.

Here is an example for the first of two event batch files:

    cd \gc2
    gc2daily
    pkzip -a c:\term\systm-a.arc bbsout.* bbsul?.* recon?.* gc2locd
    cd \bbs
    board

An hour or so later (to give the other system time to prepare its packet) the
second event activates.  Here is an example:

cd \term
terminal script.scr
rem * script calls system b and uploads it packet (systm-a)
rem * and downloads its packet (systm-B.arc)
rem * the packet generated for system a
rem * script hangs up and both systems exit to dos
pkunzip systm-b.arc \temp
rem * unarc the files to a temporary processing directory
rem * the contents of which are deleted when the event is
rem * through
cd \temp
copy bbsul1.gc2+bbsul2.gc2+bbsul3.gc2 gc2ulst
copy recon1+recon2+recon3+gc2locd gc2untl
rename bbsout.gc2 bbsin.gc2
rem * combine and rename files
copy gc2untl \gc2
copy gc2ulst \gc2
copy bbsin.gc2 \gc2
rem * copy the files over to \GC2 to be processed by GC2IMPRT
del *.*
rem * delete all the files in the \TEMP directory since we're done with them
del \term\systm-?.arc
rem * delete the old archives from the terminal program subdirectory
cd \gc2
gc2imprt
rem * import data into GC2s databases
cd \bbs
board
rem * reload the bulletin board

The BBS that receives the upload can run an event that starts at the point
where we unarced the files to the \TEMP directory.

If you develop a script for a particular communications program to move these
files between two BBSs, please call our support system (FBN Online) and upload
them so other Sysops running GC2 can benefit from your knowledge.

The above may sound complicated, but once you have it working, it will be a
BIG success and attraction with your users.  If you use PCPursuit you could
cost effectively interact with a board on the other side of the country.  That
could prove to be a very interesting game!

Users on the local system can only see intelligence data (player locations)
for their origin nation.  By getting a contact on a remote system they could
buy information (by donating money to a player on the remote system in
exchange for a message containing player locations) and so forth.  If a user
played on both systems, he could funnel money between each game as needed.
There are even more scenarios for effective use of multi-BBS interaction.


Winning Requirements

You can define the winning requirements by choosing option 6 from the main
menu of GC2EDIT.  If you have a real active system and there is a lot of
competition, consider raising the winning requirements.  If, on the other
hand, there is not much competition, consider lowering the requirements so
users can advance faster and more fairly.  The hardest rank advancement is
moving from Bounty Hunter to Spy.  Evaluate the needs of your system and
consider changing it.


Port Prices

Port prices and production can be altered by editing the ASCII file
PRICES.GC2.  It should contain 12 lines that fit the following format:

    Line 1:    Base price of ranium for a class 1 port
    Line 2:    Maximum random value that can be added to above
    Line 3:    Base price of food for a class 1 port
    Line 4:    Maximum random value that can be added to above
    Line 5:    Base price of ranium for a class 2 port
    Line 6:    Maximum random value that can be added to above
    Line 7:    Base price of food for a class 2 port
    Line 8:    Maximum random value that can be added to above
    Line 9:    Base number of holds of ranium a port will need/produce per
               night
    Line 10:   Maximum random value that can be added to above
    Line 11:   Base number of holds of food a port will need/produce per
               night
    Line 12:   Maximum random value that can be added to above

A class 1 port buys ranium from the player and sells food to the user.  A
class 2 port buys food from the player and sells ranium to the user.

The random value is the range (1 to whatever number) that can be added to the
base price, so that all port prices are not the same.


Contacting the Author, Latest Updates, and Support

The latest updates for Galactic Conquest will be found on CompuTech
Online in Conference # 32.  Please direct any inquiries or requests
for support to Michael Cleverly WITHIN CONFERENCE # 32!  If you
leave a message anywhere else on CompuTech, we cannot garauntee that
it will ever be read!  Also, the latest files can only be found
within Conference # 32.  CompuTech Online can be reached by dialing
[phone], 24 hours a day.  Speeds from 300 thru 19200 HST
are supported.


REGISTRATION

Galactic Conquest ][ is distributed under the shareware concept.
What this means is you may try GC2 out on your system for a
month.  If you feel that it meets your needs as a door you are
requested to support the author by registering it.  Many long
hours and big long distance phone bills went into the development of GC2.
Please print out fhe file "REGISTER.DOC" fill in the blanks, and
mail in with the appropriate amount.

Mail your registration to:

            Michael Cleverly
            158 East 1650 South
            Bountiful, Utah, 84010-5229

Registered users will receive the following:

           1) Registeration Serial Number.
           2) Printed Instillation Instructions.
           3) Access to CompuTech Online BBS.
           4) Future updates free via downloading from conference #32
              on CompuTech Online.


PHILOSIPHY

Previous versions of Galactic Conquest I and II were provided as shareware.
However, the maitenance program was to some degree "crippled" in the Test
Drive Version.  It would only allow a game to function for either 3 weeks
or 3 months (depending on version) before the game would have to be
re-initialized or registered.

Recently while looking at a large number of doors for the possible
inclusion of some of them on one of the BBS' I ran accross quite a
few doors that were LOCAL MODE ONLY demo's, or were stamped over
and over with a plea for money.  Some of these doors would also
not allow you to change the BBS and/or SysOps name until you
registered them.  Some of these doors were simply minor modifications
to someone elses original program!  For the record, Galactic Conquest II
is purely original code.  The GAPQBDR I/O routines used have been
registered with the author and licensed for use.  This and all future
versions of Galactic Conquest will have *NO* crippled, restrictred,
or features in the Test Drive version which aren't also available
to registered users.  The pricing of Galactic Conquest II has also been
adjusted to make it more affordable, and in line with other doors of
its type.  I have achieved fairly good response and support from the
Test Drive method implemented in the past.  Please continue to support
this new philosiphy, so that reverting back to the old method will
not become necessary.

Solutions to Common Problems

 Q. "The doors comes up and says 'Can not read' twice and then reloads
    the BBS"

A.  This indicates that the door can not read the name of the
    configuration file you are passing it.  Make sure it is a
    valid file name.

Q.  "I'm running GC2 under PCBoard and the door comes up and says
    can not read GAP.CNF.  You don't talk about GAP.CNF anywhere
    whats the deal?"

A.  The door is defaulting to GAP mode.  Be sure the CFG file
    you are passing in has a "1" on line 3 to tell the door
    to run in PCBoard mode.

Q.  "The GC2 support programs come up and say 'input runtime
     module path' and I've typed every valid path to
     BRUN45.EXE.  Whats wrong?"

A.  The support programs require the file BRUN40.EXE.  This
    file may or may not be in your ZIP.  If you don't have
    it, call BEACONetwork [phone], join the Up/Download
    conference and download BRUN40.ZIP.


Disclaimer

This product is provided "as is" without warranty of any kind.  The entire
risk as to the results and performance of the program is assumed by you.
Should the program prove defective, you (and not Michael Cleverly or his
agents) assume the entire costs of all necessary servicing, repair, or
correction.  Further, Michael Cleverly does not warrant, guarantee, or make
any representations regarding the use of, or the results of the use of the
program in terms of correctness, accuracy, reliability, currentness, or
otherwise; and you rely on the program and the results solely at your own
risk.  Michael Cleverly cannot accept responsibility for system damage, loss
of profit, or any other special, incidental, or consequential damages
resulting from the use or inability to use this product.  Michael Cleverly
makes no other warranties, expressed or implied.

Galactic Conquest II, all support programs, associated data files, and
PREPDOOR are Copyright (c) 1987, 1988, 1989 by Michael Cleverly.  All Rights
Resereved.